back door

An alternative interface to a system under test (SUT) that test software can use to inject indirect inputs into the SUT A database is a common example of a back door but it could be any component that can be either manipulated to return test-specific values or replaced by a Test Double. Contrast this with the front door.

Page generated at Wed Feb 09 16:39:09 +1100 2011

Copyright © 2003-2008 Gerard Meszaros all rights reserved

All "Glossary"

acceptance test

anonymous inner class

aspect-oriented programming

asynchronous test

behavior-driven development

built-in self test

class attribute

continuous integration

data access layer

depended-on component (DOC)

design for testability

document-driven development

dynamic binding

emergent design

endoscopic testing

equivalence class

example-driven development

expected outcome

exploratory testing

eXtreme Programming

fault insertion test

fixture holding class variable

fixture holding instance variable

fixture holding local variable

fixture teardown

fluent interface

function pointer

functional test

garbage collection

global variable

Hollywood Principle

incremental delivery

incremental development

indirect output

instance method

instance variable

interaction point

inversion of control

iterative development

layer-crossing test

legacy software

method attribute

need-driven development

object-relational mapping

observation point

outgoing interface

pattern language

per-functionality test

presentation layer

presentation logic

procedure variable

production code

programmer test

regression test

result verification

root cause analysis

round trip test

static variable

storytest-driven development

substitutable dependency

synchronous test

test maintainer

test-driven bug fixing

test-driven development

test-first development

test-last development

test-specific equality

user acceptance test